home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
btrieve
/
btr411.exe
/
BUGS.41C
< prev
next >
Wrap
Text File
|
1990-08-23
|
4KB
|
128 lines
21 February 89
Use DEBUG.COM to execute these patches under DOS. For OS/2 users,
use a DOS machine (not the compatibility box or 'real' mode) to
apply the DEBUG patches.
Rename 'Btrieve.exe' to be 'Btr.pat'
'>' denotes a DOS prompt
'-' denotes the DEBUG prompt
Available patches for Btrieve:
01) Btrieve/N (DOS 3.1 networks) only. System can hang doing a write
operation using DOS 3.3. Btrieve was issuing an incorrect DOS
instruction.
> DEBUG BTR.PAT
-e 60C1 7C 06 B4 68 90 <cr>
-w
-q
02) Btrieve/N (DOS 3.1 networks) only. Automatic transaction rollback
was not occurring when a workstation lost power. (Abort trans. does
work)
> DEBUG BTR.PAT
-e 5AEB E9 31 A8 90
-e 031F 81 BF 22 00 FF FF 75 05 E8 30 5A 42 58 FF 87 04 00 E9 BC 57 <cr>
-w
-q
03) OS/2, DOS 3.1 Btrieve. If running DOS version 4.0,
Btrieve would not load; it would return an error msg "incorrect DOS
version". Note: Single user does Not need this patch as documented
earlier.
> DEBUG BTR.PAT
-s cs:0LFFFF 03 00 0A <cr>
xxxx:yyyy
-e yyyy
03. <sp> 00. <sp> 0A. 00 <cr>
-w
-q
04) Netware Btrieve (VAP) only. Preallocation feature not working.
> DEBUG BTR.PAT
-e 7160 0A <cr>
-w
-q
05) Netware Btrieve (VAP) and IBM-PC Network Btrieve only. Accessing a
file on a local drive returns a status 20.
For Netware Btrieve (VAP): For IBM PC Network:
> RENAME BREQUEST.EXE BREQ.PAT > RENAME BREDIR.EXE BRED.PAT
> DEBUG BREQ.PAT > DEBUG BRED.PAT
-s cs:0 L FFFF 14 00 50 50 <cr> -s cs:0 L 2130 BB 14 00 <cr>
xxxx:yyyy xxxx:yyyy
-e yyyy -e yyyy
14. 05 <cr> BB. <sp> 14. 05 <cr>
-w -w
-q -q
> RENAME BREQ.PAT BREQUEST.EXE > RENAME BRED.PAT BREDIR.EXE
06) Btrieve/N (DOS 3.1 networks) only. Exclusive Open, followed by
inserts allows other stations to open the same file.
> DEBUG BTR.PAT
-e 543A 90 90 90 90 90 <cr>
-e 5071 90 90 90 90 90 <cr>
-w <cr>
-q <cr>
07) Btrieve/N (DOS 3.1 networks) only. Btrieve is not updating
position on an error such as status 54...error reading variable
length page.
> DEBUG BTR.PAT
-e 47BE 2D <cr>
-w <cr>
-q <cr>
08) OS/2 Btrieve only. When the /t parameter is specified in OS/2,
Btrieve may overwrite two bytes in the users data space. (NOTE:
use full path/filename for transaction file)
> DEBUG BTRCALLS.DLL
-s cs:0 L 7084 E8 58 0C <cr>
xxxx:yyyy
-e yyyy <cr>
E8. EB <sp> 58. 1D <cr>
-s cs:0 L 7084 C7 46 FC AD 05 C4
xxxx:zzzz
-e zzzz
C7. <sp> 46. <sp> FC. <sp> AD. CB <sp> 05. 0B <cr>
-w
-q
09) Btrieve/N (DOS 3.1 networks) only. File corruption may occur during
certain critical timing intervals. This will only happen in a heavily
loaded system with a btrieve file with many keys. One station does
insert, update, or delete of a record taking enough time for other
stations just reading records to time out (20 or 30 network requests)
and continues with the read. One of the stations which timed out must
read the same page the updating station is currently changing.
The subsequent operation from the timed out station must update this
same page.
This patch will force the subsequent update to reread the updated page.
(NOTE: This patch uses SET DIRECTORY operation space, thus any programs
which use the function will need to be changed because it will return
a status 1).
> DEBUG BTR.PAT
-e f74 89 47 2c ff 47 04 e9 6e 34 <cr>
-e 43de e9 93 cb <cr>
-e 7058 63 <cr>
-e 789c 0 0 <cr>
-w <cr>
-q <cr>